NoStop 1.1 by J. Scott Sanbar Advanced Micro Consulting 1507 N. Rockwell Oklahoma City, OK 73127 (405) 787-9185 or (405) 787-9379 CIS: 73760,3304 FidoNet: 1:147/55.2 This archive should contain the following files: NOSTOP.SYS - the NOSTOP installable device driver NS.COM - the NOSTOP command line installable module (TSR) NSCONFIG.EXE - the NOSTOP command line configuration program NOSTOP.TXT - this explanitory document SUMMARY: NOSTOP consists of a device driver, a TSR and a configuration program. Either the device driver (NOSTOP.SYS) or the TSR (NS.COM) may be used to install NOSTOP. Both may be used simultaneously without conflict, but there is no added functionality. NSCONFIG.EXE is a command line configuration program to selectively enable/disable the keystrokes that NOSTOP disables. Do not attempt to load the device driver NOSTOP.SYS twice in your CONFIG.SYS or NSCONFIG.EXE will be non-functional. Once either the TSR or the device driver are installed, by default pressing CTRL-C, CTRL-BREAK or CTRL-ALT-DEL will have no effect - the keystrokes are essentially discarded. This makes DOS, many programs and batch files virtually unstoppable from the keyboard. NOSTOP also disables the CTRL-2 and ALT-3 (Keypad) methods of flagging CTRL-C. Any or all of these keystrokes can be re-enabled at any time using NSCONFIG.EXE. NOSTOP was developed mainly for use on networks. The device driver (NOSTOP.SYS) was developed to provide complete lockout for client PC's that automatically log onto the network at boot-up and never give the user access to the command line. In such a situation, batch files and/or menuing programs can be used to allow the user to navigate while at the same time restricting access to vital resources. NOSTOP ensures that they will be unable to break out of the restricted environment. NS.COM was developed mainly for foreign language users. It allows users to install NOSTOP from the AUTOEXEC.BAT after KEYB.COM, or DOS 4.0 and up users from the CONFIG.SYS using "INSTALL=" in your CONFIG.SYS after a similar command to load KEYB.COM. It also contains a feature useful when executed at the end of a network log-on script, as with Novelle's Netware. See below for details. USING NOSTOP.SYS: TO USE: simply include this line in your CONFIG.SYS file that resides in the root directory of the boot disk: DEVICE=NOSTOP.SYS The above assumes NOSTOP.SYS resides in the root (\) directory of the boot disk. If NOSTOP.SYS resides in some other directory you must include a path. For instance, if NOSTOP.SYS resides on the C: drive in the \UTILITY subdirectory: DEVICE=C:\UTILITY\NOSTOP.SYS NOSTOP.SYS should be included as the last driver in the CONFIG.SYS file, so that it will have first shot at handling the key combinations. Once installed, all the respective key combinations will be disabled, so the autoexec.bat can be run to bring up the network or run a menuing system or other batch files without possibility of breaking out. Also, NSCONFIG.EXE (described below) can be run from the AUTOEXEC.BAT or as an option for the administrator, perhaps accessed via password, to enable or disable any of the keystrokes at any time. USING NS.COM: NS.COM is a TSR (Terminate and Stay Resident) program. It has two main uses. The most important is use when language users other than english use KEYB, which will disable NOSTOP if loaded after it. Secondly, it can be used to load NOSTOP at any time after boot up, or in the AUTOEXEC.BAT, for whatever reasons. You may attempt to load it more than once, and it will give no errors, but if it detects itself already loaded, it will not load again. To use NS.COM, just include the line: D:\PATH\NS in a batch file, or type it from the command line where D is the drive and PATH represents the path to the file. If NS.COM resides on your current PATH, just type: NS If NS is on the C: drive and in the Utility directory, type: C:\UTILITY\NS A NOTE FOR FOREIGN LANGUAGE USERS: Keyb will disable NOSTOP if loaded after it. To remedy this, include the command NS after KEYB in the autoexec.bat. If you are using DOS 4.x or higher, you can use the INSTALL= command to load NOSTOP in your CONFIG.SYS after KEYB: INSTALL=C:\DOS\KEYB.COM.... INSTALL=C:\UTILITY\NS.COM YOU MUST USE INSTALL=!!! If you use INSTALL= for Keyb then just load NOSTOP.SYS after it, it will not work correctly since the INSTALL'd programs are loaded after others, and to work correctly, NOSTOP must be loaded after KEYB. There is also a use of NS.COM designed specifically for logging onto networks, especially NOVELL networks, from a log-on script. You can instruct NS.COM to execute a command immediately after it loads, for instance, starting a batch file that runs a menuing system. For instance, in a NOVELL log-on script, you can execute a command upon leaving it. By including NS and telling NS to execute another command, you can both load NS and start a batch file after leaving the log-on script. To instruct NS.COM to execute a given command on exit, include the name of the executable file or batch file or dos command preceded by and "@". For instance: NS @DIR Will install NOSTOP and do a directory listing. NS @MENUNAME Will run either a batch file or executable whose file name (excluding the extension) is MENUNAME. You may include up to 14 characters after the @, including spaces or separators. For a NOVELL script, this gives just enough room to include a drive letter and a full 8 letter file name since the same rule applies to its command for running a program after the logon script: NS @D:FILENAME 12345678901234 USING NSCONFIG.EXE: NSCONFIG.EXE is the sister program that allows enabling/disabling of the various key combinations NOSTOP.SYS is able to capture. Syntax: NSCONFIG [C][B][W][2][3] where: C or c enables CTRL-C (ie, allows it to pass through untouched) B or b enables CTRL-BREAK W or w enables warm boot (CTRL-ALT-DEL) 2 enables CTRL-2 3 enables ALT-3(Keypad) NSCONFIG can be called as often as needed, and the results are absolute, not additive. NOSTOP.SYS defaults, on installation via CONFIG.SYS to all respective keys disabled. Then, you can enable the desired keys in the AUTOEXEC.BAT or via the command line as needed. Examples: NSCONFIG - disables all keys NSCONFIG W - disables everything but warm boot NSCONFIG 2w3 - disables everything but warm boot, CTRL-2 and ALT-3 NSCONFIG CBW23 - enables all key combinations NSCONFIG c b w - error, no spaces allowed The various switches (C, B, W, 2 and 3) may be in any order, but no spaces are allowed between them. You may also enter: NSCONFIG ? For syntax help. All the files as listed above are fully copyrighted, including this text file. NOSTOP is shareware. You may use it freely and distribute it in its original form as long as all the files listed above are included, unaltered. If you wish to use NOSTOP, you MUST send a $5.00/computer registration fee to the address below: J. Scott Sanbar 8100 Glenwood Oklahoma City, OK 73114 CIS: 73760,3304 You may use NOSTOP.SYS for a trial period of TEN (10) days after which time you must either register or discontinue its use. The $5.00 fee is on a per computer basis, so if you are on a network and have 5 computers that use NOSTOP.SYS or NS.COM, the registration fee would be $25.00. For installations with extremely large numbers of computers, contact me on CompuServe or via mail to discuss a reasonable agreement for a site license, or give me a call. NOSTOP.SYS may not work with 386 protected mode operating environments like Windows 3.x. IE, NOSTOP will not disable warm boot under Windows 3.x in 386 Enhanced mode, although it will work fine in real or standard mode and will still throw away CTRL-BREAK, CTRL-2, ALT-3 and CTRL-C. NOSTOP.SYS, NS.COM, NSCONFIG.EXE and this text file are all: Copyright (c) 1991 by J. Scott Sanbar. All Rights Reserved. Shareware ----------------end-of-author's-documentation--------------- Software Library Information: This disk copy provided as a service of Public (software) Library We are not the authors of this program, nor are we associated with the author in any way other than as a distributor of the program in accordance with the author's terms of distribution. Please direct shareware payments and specific questions about this program to the author of the program, whose name appears elsewhere in this documentation. If you have trouble getting in touch with the author, we will do whatever we can to help you with your questions. All programs have been tested and do run. To report problems, please use the form that is in the file PROBLEM.DOC on many of our disks or in other written for- mat with screen printouts, if possible. PsL cannot debug pro- programs over the telephone, though we can answer questions. Disks in the PsL are updated monthly, so if you did not get this disk directly from the PsL, you should be aware that the files in this set may no longer be the current versions. Also, if you got this disk from another vendor and are having prob- lems, be aware that some files may have become corrupted or lost by that vendor. Get a current, working disk from PsL. For a copy of the latest monthly software library newsletter and a list of the 4,000+ disks in the library, call or write Public (software) Library P.O.Box 35705 - F Houston, TX 77235-5705 1-800-2424-PSL MC/Visa/AmEx/Discover Outside of U.S. or in Texas or for general information, Call 1-713-524-6394